Skip to main content

UI Dynamic for Crestron

Put your own buttons on a Crestron Home tile — and make them do anything that speaks HTTP.

Crestron Home is a closed world: it drives the devices it has drivers for, and nothing else. UI Dynamic opens it up. You build a tile of buttons, toggles and status controls in a browser, and each one can fire an HTTP request to anything on the network — a Shelly relay, a Tasmota plug, a Hue bridge, Home Assistant, a garage controller, a REST API. In the other direction, anything that can send an HTTP request — Home Assistant, Node-RED, IFTTT, a doorbell — can set a control's state or fire a Crestron Home event, and therefore a scene.

It is a bridge between Crestron Home and everything Crestron never wrote a driver for.

What it does​

A room tile with the controls you define. Each control has one or more states, each state a label and an icon, and each state or press can fire a list of HTTP requests.

  • Buttons that call HTTP. A press fires a request — with a templated URL, body and headers, optional authentication, and a per-request delay so a list of requests becomes a macro ("unlock the gate, wait two seconds, turn the light on").
  • States set by webhooks. A URL you hand to Home Assistant or a doorbell sets a control's state or fires a Crestron Home event. The event drives a scene, a schedule, anything Crestron programming can react to.
  • Every control is a programming surface. Each control's states and presses appear in Crestron Home programming as named events ("Kitchen Fire — On"), and the driver exposes actions to set state, toggle, press and drive the tile from a scene or schedule.

Controls come in a few shapes — a two-state button, a toggle, a status line with a button, a toggle with a slider, and a multi-step control that cycles through any number of states (Off → Low → Medium → High).

Configured in a browser, on the local network​

Controls are built in a browser app served from the processor, not through the driver's settings pages.

  • Add, name and reorder controls, and give each state a label and an icon.
  • Build the HTTP requests each state and press fires — method, URL, body, headers, authentication.
  • Send a test request from the browser and see exactly what came back — status and response body — without a trip to the processor console. A mistyped header is caught here, not on site.
  • Copy a webhook URL per control, ready to paste into Home Assistant or a doorbell.
  • Read the activity log — the last hundred calls in and out, with outcomes, so you can see what arrived and what went out.

What you need​

  • A licence — a 30-day trial and full keys are available from the LCD store. Existing CHUIDYNAMIC licence keys carry over (see below).
  • Network reachability between the processor and whatever the buttons call. For outbound HTTP that is the LAN device or the internet endpoint; for webhooks it is whatever sends them.
  • Nothing else. There is no cloud account and no extra hardware.

Upgrading from the previous UI Dynamic driver​

This is a new driver on the Crestron Home entity model, and it is not an in-place upgrade. The site must be set up again in the new browser app.

Two things to know:

  • Your existing licence key still works. The driver keeps the same product SKU (CHUIDYNAMIC).
  • Your existing buttons can be brought across with a one-off converter, so you do not have to rebuild them by hand. The Crestron Home programming that referenced the old buttons is not migrated — those bindings point at the old driver and must be rewired. See Migrating from the previous driver.